coinos-ui.git/src/routes/(app)/invoice/[id], branch master

invoice: a reusable bolt12 offer has no terminal paid state

2026-09-22T18:27:15Z

A bolt12 offer is a standing payment code. CLN derives the same offer_id from the same (amount, description), so re-creating one hands back the original record, whose `received` has accumulated over the offer's whole lifetime. The invoice layout read that as "this invoice was paid" and redirected to the success screen, so reopening a long-lived offer never showed the QR and left no way to copy the lno. Treat a payment as celebratory only when it arrives while the page is open: the socket handler now passes the amount of that payment as `?paid=`, and the layout uses it in place of the lifetime total for reusable offers. Single-use invoices keep the existing logic, so a partly-paid invoice still stays on the QR rather than celebrating early. The success screen showed lifetime `received` for the same reason, which misreported a single payment to a long-lived offer; it now renders the amount the socket reported, which is already net of tip. Co-Authored-By: Claude Opus 5 (1M context)

receive/invoice: build POST body from snapshot, don't mutate $derived

2026-06-19T07:09:21Z

The merchant receive and invoice pages mutated the $derived `invoice` proxy (setType/setAmount/setMemo) then POSTed it. Mutating a $derived and JSON.stringify-ing it serializes unreliably, so a stale type (on-chain when lightning was expected) and a stale/10x-shifted amount could leak from a prior interaction into POST /invoice (funk POS bug). Build the body as { ...$state.snapshot(invoice), ...changes } so the intended type/amount/address_type reliably win; update() takes the plain body. Front-end only. Co-Authored-By: Claude Opus 4.8 (1M context)

redirect to paid route

2025-09-09T19:38:40Z

check for user in invoice route

2025-09-09T16:18:11Z

fix autopay with tip logic

2025-08-27T04:53:38Z

set tip

2025-08-21T06:20:02Z

handle null tips

2025-07-20T05:56:05Z

prompt for tip for auto pays

2025-07-20T01:07:57Z

fix pin issue

2025-07-16T07:05:35Z

user onboarding

2025-07-10T19:36:50Z